Lighting device and apparatus with multiple applications for processing a common sensed condition

ABSTRACT

A lighting device or an apparatus for use with a light source has one or more sensors, intelligence in the form of programmed processors and communication capabilities. Each sensor is configured to monitor one or more conditions external to a lighting device not directly related to operational performance of the respective lighting device. Programming provides a standardized interface to enable processing of sensed conditions from sensors of different types.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/463,586, Filed May 3, 2012, entitled “NETWORKED ARCHITECTURE FORSYSTEM OF LIGHTING DEVICES HAVING SENSORS, FOR INTELLIGENTAPPLICATIONS,” the disclosure of which is entirely incorporated hereinby reference.

This application is related to U.S. application Ser. No. 14/285,881,filed May 23, 2014 entitled “LIGHTING DEVICES WITH SENSORS FOR DETECTINGONE OR MORE EXTERNAL CONDITIONS AND NETWORKED SYSTEM USING SUCHDEVICES,” which is a continuation of U.S. application Ser. No.13/463,594, filed May 3, 2012 entitled “LIGHTING DEVICES WITH SENSORSFOR DETECTING ONE OR MORE EXTERNAL CONDITIONS AND NETWORKED SYSTEM USINGSUCH DEVICES,” now U.S. Pat. No. 8,755,039, the disclosures of whichalso are entirely incorporated herein by reference.

TECHNICAL FIELD

The present subject matter relates to a system and components of thesystem forming a network of lighting devices, with sensors, intelligenceand communication capabilities to monitor one or more conditionsexternal to the lighting devices not directly related to operationalperformance of the respective lighting devices, for a variety ofapplications separate and in addition to the lighting related functionsof the networked devices.

BACKGROUND

Electrical lighting has become commonplace in modern society. Electricallighting devices are commonly deployed, for example, in homes, buildingsof commercial and other enterprise establishments, as well as in variousoutdoor settings. Even in a relatively small state or country, there maybe millions of lighting devices in use. Traditional lighting deviceshave tended to be relatively dumb, in that they can be turned ON andOFF, and in some cases may be dimmed, usually in response to useractivation of a relatively simple input device. Lighting devices havealso been controlled in response to ambient light detectors that turn ona light only when ambient light is at or below a threshold (e.g. as thesun goes down) and in response to occupancy sensors (e.g. to turn onlight when a room is occupied and to turn the light off when the room isno longer occupied for some period). Often such devices are controlledindividually or as relatively small groups at separate locations.

With the advent of modern electronics has come advancement both in thetypes of light sources and in the control capabilities within thelighting devices. For example, solid state sources are now becoming acommercially viable alternative to traditional light sources such asincandescent and fluorescent lamps. By nature, solid state light sourcessuch as light emitting diodes (LEDs) are easily controlled by electroniclogic circuits or processors. Electronic controls have also beendeveloped for other types of light sources. Advanced electronics in thecontrol elements have facilitated more sophisticated control algorithmsas well as increased networking of lighting devices.

Sensing and network communications, however, have focused on thelighting functions/applications of the lighting devices. For example,sensors may be provided in a lighting device to detect parametersrelevant to control operation of the lighting device, and the processorin the device controls the source(s) of the device in response to thesensor inputs. Alternatively or in addition, a communication interfacein each of a number of networked lighting devices may allowcommunication about the status of each lighting device to a systemcontrol center. A programmed computer or a person at the control centerthen may be able to send commands to individual lighting devices or togroups of lighting devices, for example, based on a decision responsiveto one or more conditions sensed by some or all of the lighting devices.

However, these advances in lighting devices and networked systems havemainly addressed aspects of the lighting provided by the lightingdevices. For example, lighting devices may be adjusted, turned ON and/orturned OFF based on monitored conditions, either by processor logicwithin the device(s) or commands from a central control. It also hasbeen suggested that networked lighting devices could provide transportfor data communications to/from other devices that may come within rangeof the lighting device and/or its internal communication interface.

It is also useful to monitor and respond to a wide range of otherconditions that do not directly relate to lighting. A vast array ofsensor types exists for sensing various conditions. In the home, forexample, smoke, fire, carbon monoxide and burglary sensors are common.Often such sensing is locally implemented by individual sensing units,with no coordination. In more sophisticated installations, a number ofsensors of various types may be couple to a communication device orsystem, which provides communications to a central system that monitorsa number of enterprise premises or a number of individual customerlocations. However, the individual devices and the networked monitoringsystems have traditionally been separate and independent from thelighting devices in or at the monitored locales. Even in systems thatprovide combinations of lighting control and condition monitoring and/orcommunications related to both functions, the lighting and monitoringequipment are separate devices on the premises with separate power andcommunication capabilities.

Hence, there is still room for further improvement in lighting andmonitoring technologies.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a functional block diagram of an exemplary system ofintelligent lighting devices and hierarchical layers of controlcomputers.

FIG. 2 is a functional block diagram of the elements in a first exampleof an intelligent lighting device that may be used as one of thelighting devices in the system of FIG. 1.

FIG. 3 is a functional block diagram of the elements in a second exampleof an intelligent lighting device that may be used as one of thelighting devices in the system of FIG. 1.

FIG. 4 illustrates another intelligent lighting device that may be usedas one of the lighting devices in the system of FIG. 1.

FIG. 5 is a functional block diagram of a monitoring and communicationmodule used in an example of an intelligent lighting device like that ofFIG. 4.

FIG. 6 is a is a simplified functional block diagram of a computer thatmay be configured as a host or server, for example, to function as theone of the control computers in the system of FIG. 1.

FIG. 7 is a simplified functional block diagram of a personal computeror other user terminal device, which may be used as a control computeror in communication with a server implementation of a control computer,in the system of FIG. 1.

FIG. 8 is a simplified functional block diagram of a mobile device, asan alternate example of a user terminal device, which may be used as acontrol computer or in communication with a server implementation of acontrol computer, in the system of FIG. 1.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent to those skilledin the art that the present teachings may be practiced without suchdetails. In other instances, well known methods, procedures, components,and/or circuitry have been described at a relatively high-level, withoutdetail, in order to avoid unnecessarily obscuring aspects of the presentteachings.

The various examples disclosed below relate to systems and components(e.g. lighting devices and control computers) forming a network ofintelligent lighting devices with sensors to monitor one or moreexternal conditions. Reference now is made in detail to the examplesillustrated in the accompanying drawings and discussed below.

By way of an example, FIG. 1 shows a system 10 that forms a network ofintelligent lighting devices 11, here configured as light fixtures byway of example. The system 10 is logically organized in a hierarchicalmanner represented by Layers L1 to L4 (separated by dashed horizontallines in the drawing). In this example, the lowest layer L1 of thehierarchy is the layer formed by the intelligent lighting devices, inthis case, light fixtures 11. The system 10 also includes a hierarchicalarrangement of two or more layers of control computers, represented byvarious types of host/server computers and user terminal computers inthe upper three layers L2 to L4 in the example of FIG. 1.

At the lower level L1, a number of light fixtures 11 are organized intoeach of several groups; and a first layer or local control systemcomputer communicates with some number of respective groups. In thesimple system example of FIG. 1, several light fixtures 11 are logicallyorganized as a first group G1A, and another set of light fixtures 11 arelogically organized as a first group G2A. These two groups of lightfixtures G1A, G2A communicate with a local control server/host typecomputer 13A and possibly a local user terminal type computer 15A in theL2 layer via a communication network represented by way of example bythe local area network 17A. Similarly, several light fixtures 11 arelogically organized as a group G1B, and another set of light fixtures 11are logically organized as another group G2B. These two groups of lightfixtures G1B, G2B communicate with a local control server/host typecomputer 13B and possibly a local user terminal type computer 15B in theL2 layer via a communication network represented by way of example by asecond local area network 17B.

The techniques discussed here are applicable to a wide range of lightingapplications/systems/configurations. For example, in some sets ofgroups, the light fixtures may be outdoor lights such as street lamps orparking lot type lighting devices. In a street lamp example, groups oflighting devices might be those for one or some number of city blocks.For purposes of further discussion of the example of FIG. 1, we willassume that the lighting devices 11 are devices within one or morebuildings of one or more enterprises. So, for example, the lightingdevices 11 in each of groups G1A and G2A could be the devices forlighting a particular floor or floors of a first building; and thelighting devices 11 in each of groups G1B and G2B could be the devicesfor lighting a particular floor or floors of another building. In suchan enterprise building example, the local host/server computer 13A mightserve as a building control system (BCS A) for the first building,whereas the host/server computer 13B might serve as a building controlsystem (BCS B) for the second building, although for other types oflocal organizations of the fixtures the L2 layer computers may bereferred to by other designations such a local control systems or localcomputer systems. The terminals 15A, 15B would communicate via thenetwork 17A or 17B with the respective BCS A 13A or BCS B 13B, althoughin some instances, the terminals may also communicate through a networkdirectly with the light fixtures in the respective building or the like.

Although public networks could be used, in the building example, thenetworks 17A, 17B for communications between the intelligent lightingdevices 11 and the respective control computers 13A, 15A, 13B, and 15Bin each premises are implemented as local area networks (LANs) withinrespective buildings. Each LAN may be wired (e.g. metallic or opticalfiber), wireless (e.g. radio frequency or free space optical) or acombination of such network technologies. For example, one building mayuse a wired Ethernet network, whereas another may use a wireless networksuch as a wireless Ethernet (WiFi) network. A wired network may utilizethe lines that supply power to the light fixtures and/or the computers,or a wired local network may use separate optical or electrical networkwiring. Of course, different buildings or other groups of intelligentfixtures may use different types of LANs. In an outdoor example, e.g.for implementing intelligent fixtures as street lights, the fixtures mayutilize power line communication technology, cellular networktransceivers, or a wireless mesh communication network topology.

The BCS type computer may be implemented with any suitable computerplatform capable of running desired programming for monitoring andcontrol functions and handling the desired work/traffic load expectedfor the number of intelligent light fixtures with which the particularsystem 13A or 13B will be working. Each enterprise or building may haveone or more of the user terminals 15A, 15B. The user terminal equipmentmay be implemented with any suitable processing device that can alsooffer a suitable user interface. The terminal 15A, for example, is shownas a desktop computer with a wired link into the first LAN 17A, and theterminal 15B is shown as a touchscreen type tablet computer with awireless link into the second LAN 17B. However, other terminal types,such as laptop computers, notebook computers, netbook computers, andsmartphones may serve as the user terminal computers of layer L2.

In the exemplary four tier hierarchy, computers 13A, 13B, 15A and 15Bare the first layer computers (in exemplary layer L2) in communicationwith the light fixtures 11 in layer L1. Depending on the number oflighting devices and installations/locations thereof, there may becontrol computers in one, two or more higher layers. In our buildinginstallation example of FIG. 1, there are any number of buildings withinstalled light fixtures 11 and associated building control system (BCS)computers within a geographic area or region. The BCS (computers andpossibly the terminal devices) in layer L2 communicate with a computeror computers in the higher layer(s) via a network. Hence, in theexample, each building installation includes a gateway and/or firewall(GTWY/FW) 19A, 19B enabling communications of the variouselements/devices connected to the LANs 17A, 17B via a wide area network(WAN) 21. A GTWY/FW provides the requisite communication interfacing andsecurity enforcement for communications between the routers implementingthe LAN and routers of the WAN 21. The WAN 21 may be the publicInternet, or a private intranet operated by an enterprise or a serviceprovider. As in the lower layer network communications, the linksbetween the LANs and the WAN may use any available/practical wired orwireless technology or any commercially advantageous (cost effective)combination thereof.

The WAN 21 enables the computers in layer L2 to communicate withcomputers implementing one or more higher layers L3, L4, etc. of thenetworked architecture of system 10. For example, some number of BCScomputer systems within a particular region or area may communicate witha regional or area control system (ACS) computer at the L3 level. In theillustrated example, the computers BCS A 13A and BCS B 13B communicatevia the WAN 21 with a computer system ACS A 23A. Although the lowerlayer elements are not shown for convenience, in another area, BCScomputers would communicate via the WAN 21 with a computer system ACS B23B serving as the L3 control computer for the second region or area. Asrepresented generally by the tablet computer 25, layer L3 may alsoinclude control computers in the form of various user terminal devicesof any of the types discussed earlier relative to devices 15A and 15B inlayer L2. Depending on secure authorization policies, a user of aterminal such as 25 may interact with either or both of the ACScomputers in layer L3, via the WAN 21. Other regions may be served by L2and L3 host/server computer systems and/or user terminal devices in asimilar manner. Each of the computers in layer L3 may be coupled orlinked to the network 21 via any suitable wired or wireless technology.

In an example like that shown that encompasses a number of differentareas or regions, the area computers (ACSs) 23-25 in layer L3 in turncommunicate with one or more computers in a still higher layer L4 of thenetworked system hierarchy. The communications may utilize a differentnetwork, or as illustrated, the computers 23-25 of layer L3 maycommunicate with the computer(s) of the higher layer L4 via the WAN 21.As the system 10 expands to cover wider geographic areas and to workwith larger numbers of lighting devices, the system may be expanded toadd further layers to the hierarchy, either in-between the exemplarylayers or as still higher layers.

In the four tier example, the L4 layer is the top logical layer. Hence,the example includes a central control system (CCS) computer 27 at thatlayer. Either in association with or as an alternative to the CCS 27,the L4 layer may include a user terminal 29. Although shown as a desktopterminal 29, the user terminal may be any appropriate type of computerdevice, as discussed above with respect to terminal devices 15A, 15B and25 in the L2 and L3 layers. Each of the computers in layer L4 may becoupled or linked to the network 21 via any suitable wired or wirelesstechnology.

Returning to the lower L1 layer in our example, we will next considerthe high-level aspects of the intelligent light fixture, with specificreference to elements shown within one of the fixtures in the group G2A.More specific details will be discussed later with regard to severalexamples shown in FIGS. 2-6.

As shown at a high level in FIG. 1, each lighting device 11 includes alight source 31, a sensor coupling 33 and a sensor 35 for sensing atleast one external condition not related directly to operations orcommunications of the light fixture. The networking and relatedmonitoring and control operations discussed here can be utilized withany desired light source, and different fixtures in the same ordifferent buildings or outdoor locations can utilize different lightsources to suit the needs of various lighting applications of thefixtures. Each light fixture 11 may be configured with a single coupling33 and external condition sensor 35, although the example in FIG. 1shows two such couplings and sensors in each fixture, e.g. so that eachfixture can sense two different external conditions (or the samecondition, for example, in different directions or locations around thefixture or to provide a combined reading and thereby improve overallaccuracy).

A fixture 11 may include one or more feedback sensors for sensingoperational conditions, such as source or circuit temperature, lightoutput intensity, or one or more other characteristics of the lightproduced by the source, which relate to operation of the fixture. Someor all of the fixtures may have light activation related sensors, suchas ON/OFF switches, room occupancy sensors, ambient light sensors forcontrolling lighting in response to ambient light intensity, and lightdimmers. Feedback and light activation sensors are referred tocollectively as internal sensors, in that they sense aspects of and/oruser inputs to control the internal lighting operations of one or moreof the fixtures. In the example, the illustrative fixture in group G2Aincludes a coupling 37 and at least one internal condition sensor 39.

Each of the light fixtures 11 is configured to sense at least oneexternal condition not related directly to operations or communicationsof the light fixture. As discussed more later, each fixture also has aninterface for communications with other system elements. The conditionor conditions detected by sensors 35 are external in that they relate tosome aspect observable in the environment around and near the fixture 11other than those relating to the feedback, normal lighting controland/or communications of the fixture 11. Although more examples will bediscussed later, a few examples of conditions that may be detected viaexternal sensing include ambient temperature, humidity, air pressure andwind speed in the surrounding environment; images of nearby objects;motion outside the fixture; gases and other substances in theatmosphere; and temperature and moisture on objects within some distancerange of the fixture 11. As such, some of the external conditions, likeair temp, air quality, and vibration, relate to ambient conditionsaround or near the fixture itself; whereas other external conditions,like reflected or directed light, or like an image or a video of adistant object, relate to external remote conditions that exist at somedistance from fixture.

A wide variety of sensor devices may be used to sense any one or more ofthese or other types of external conditions. For example, the sensor maybe an optical device, for sensing one or more characteristics of lightin the ultraviolet, visible or infrared portions of the electromagneticspectrum. Optical devices may be used, for example, for sensingdirection of light and determining position of an object as described inU.S. Pat. Nos. 6,043,873 and 5,705,804 both by Ramer et al. Otherexamples of optical sensors include linear and two-dimensional imagingdevices.

By way of another example, a lighting device 11 may include a sensor inthe form of a Micro-Electro-Mechanical System (MEMS) for sensing motion,similar to gyroscopic devices used in smartphones and the like to senseorientation, movement and direction. Here, MEMS type sensors would sensemagnitude and directions of vibrations of the fixtures 11 due toexternal forces. Collective analysis, for example, might indicate anearthquake and the area and magnitude of the impact.

The external condition sensor coupling 33 is configured to present asensor connection interface standardized across at least some number ofthe lighting devices 11. The standardized connection interface iscompatible with different types of external condition sensors 35. Eachsensor 35 is connected to the standardized connection interface of thesensor coupling 33. In this way, one configuration of the coupling 33may be used with different types of sensors. Within any one fixture,there may be one, two or more couplings 33 configured to the samestandard as well as one, two or more other couplings 33 configured toone or more additional standards.

Each sensor 35 is a device of one of the types compatible with thestandardized interface provided through a standardized coupling 33. Thelocation of each sensor 35 enables sensing of a condition external tothe respective lighting device 11, although the condition is notdirectly related to operational performance of the respective lightingdevice. Each sensor 35 is configured to output a signal responsive tothe particular sensed external condition via the standardized connectioninterface of the associated sensor coupling 33.

A “sensor” may be as simple as a condition responsive transducer forgenerating an electrical signal bearing a known relationship to theamount or degree or the like of a particular condition that thetransducer detects. However, most implementations, particularly those inthe examples, utilize sensors that include at least some circuitry forprocessing the output of the transducer(s) included as part of thesensor. The circuitry receives the signal from the transducer(s) in thesensor and produces an output via the coupling that conforms to thesignaling aspects of the sensor coupling standard, e.g. as a standardanalog level signal on one or more pins designated for an analogconnection and/or as appropriately formatted data on the pins designatedfor data outputs. The electronics of such a sensor may also receive andrespond to a signal received from the I/O interface on the board.

Each lighting device, in this case each fixture 11, also includesprocessing and communications elements, represented collectively in thehigh-level functional block diagram of FIG. 1 by thecontrol/communication (Ctrl./Comm.) board 41. These elements, forexample, include a processor, which is coupled to the sensor coupling(s)33 in the fixture 11, for processing data responsive to the signal fromeach included external condition sensor 35. If internal sensing isprovided, the processor also is coupled to the sensor coupling(s) 37 inthe fixture 11, for processing data responsive to the signal from eachincluded internal condition sensor 39.

The elements on the control/communication board 41 also include amemory, accessible to the processor, which stores programming forexecution by the processor and data for processing or that has beenprocessed by the processor during program execution. For example, thememory stores a program corresponding at least in part to each type ofincluded external condition sensor 35. Execution of the program controlsat least one function of the processor of the light fixture 11responsive to the external condition sensed by the sensor 35, such ascollection of data regarding sensed external condition(s) and relatedcommunications with at least one of the higher layer computers of thesystem 10.

Each light fixture 11 also includes a communication interface accessibleby the processor. The communication interface is configured to enablethe processor to communicate information resulting from performance ofthe function of the processor controlled by the program responsive tothe sensed condition through the communications network, in the example,through a LAN 17A or 17B.

In the exemplary four tier hierarchy, computers 13A, 13B, 15A and 15Bare first layer computers having communications interfaces enabling eachof those computers to communicate through the communications networks17A, 17B with a different respective group of the fixture type lightingdevices 11. In this way, each first layer computer can receiveinformation from the processors of its respective groups of lightingdevices. At least one of the first layer computers in communication witheach group of lighting devices 11 is configured to process the receivedinformation to obtain resultant information.

In the exemplary four tier hierarchy, any of the computers 23-25 inlayer L3 and/or computers 27-29 in layer L4 would be a second layercomputer having a communications interface to communicate through thecommunications network (WAN 21) to receive the resultant informationfrom first layer computers. The second layer computer is configured toinitiate at least one action in response to processing of the resultantinformation received from the first layer computers.

Each of the various computers in the layers L2 to L4 will runprogramming to control respective operations thereof includingoperations for processing condition related data and/or responsivecommunication and related actions. Although possibly somewhat differentin each type of computerized device, each will run an operating system(OS) and one or more applications programs (APs) related to the sensedcondition communication and processing functions of the system 10. TheOS of a particular type of computerized device will provide anapplication programming interface (API) to allow various applicationprograms to run on the computerized device via the respective OS and inthat way utilize the various resources and functions of the computerizeddevice. For example, the API in computerized devices at one or both thehigher layers L3 and L4 of computers enables application programming forprocessing the condition-related data and initiating the responsiveaction can be written to the standardized API. In this way, it becomespossible for various parties to write application programs for thehigher layer programs to respond to different types of conditions sensedby the lighting devices 11 and support different functions desired bythe parties that utilize the system 10.

The computer or computers in layer L4 that receive the processedinformation from the layer L3 computers can initiate one or moreresponsive actions. The actions may involve any one or more of a varietyof reporting functions, such as sending alerts to terminal devices ofusers who may need to know or response, generating periodic reports, orthe like. The action or actions also may involve generating lightingrelated commands to send back down through the system 10 to cause one ormore of the intelligent lighting devices 11 to modify their operationsand/or to sending commands through the system 10 to cause one or more ofthe intelligent lighting devices 11 to collect and send and additionalcondition related information.

As outlined above, the external condition monitoring, collection of dataobtained and processing of external condition data, from lightingdevices 11 over a region or area of significant size admits of a widerange of possible applications for the data. The actions that may beinitiated from the high level computer may be as wide ranging as thearray of possible applications of the monitoring and data processingcapabilities of the system 10. For example, the high level computer(s)may generate maps or other forms of reports relating to conditionsexisting across the monitored region(s). Where the sensed conditionsinclude atmospheric conditions, such as pollution, a map might show thespread of a particular sensed pollutant allowing government personnel toidentify the source, track the spread and/or initiate remedial actions.Weather related data collected at a multitude of street and highwaylamps would provide much more granular information about weatherconditions than is typically available from remote weather monitoringstations today. The maps or other reports generated at the higherlevel(s) of the system 19 or portions of such information may bedistributed through the network to terminal devices of users throughoutthe effected area, including devices shown in the lower layers of thesystem 10. As another map example, if sensing of position of objectsnear lighting devices or sensing vibration of the lighting devices isprocessed to determine the occurrence and magnitude of an earthquake, amap might illustrate the relative magnitude of the quake throughout anarea impacted by the quake.

To facilitate the data processing, at least the computer(s) at layer L4have access to information about the positions of the lighting devices11 to facilitate the relevant processing and related actions. Typically,the position information is known in advance and maintained in adatabase. Maps of the area(s) or region(s) can be correlated with someor all of the position information. An alternative to the positiondatabase would be to include a position detection device, such as aglobal satellite positioning (GPS) receiver and associated positioncalculation programming in the lighting devices. This later approachwould allow for reporting of position changes, e.g. in response tomovement of the fixture if not permanently mounted and/or if taken downand moved for some reason.

As another example of responsive action, the action initiated in thehigh level computer may relate to further control of lighting operationsof one or more of the lighting devices 11. For example, in a situationwhere the sensed conditions indicate an emergency in a building, thecontrol action may involve sending commands back down through the system10 to selected lighting devices 11 so as to initiate operations of anynumber of lighting devices in the effected building, e.g. to help peopleto evacuate the building and/or to help responders to find the source ofthe emergency condition.

As noted earlier, another type of action initiated by the high levelcomputer may involve generating commands to send back down through thesystem 10 to cause one or more of the intelligent lighting devices 11 tocollect and send any additional condition related information. To helpwith damage assessment in the earthquake detection example, thesecommands might cause lighting devices having image sensors to captureand send back images or videos for assessment.

The elements of the system 10 may be owned and operated by one entity,such an enterprise with multiple buildings distributed over a number ofdispersed geographic regions. In a street light example, a counsel ofgovernments for a city and surrounding suburbs may jointly operate thelight fixtures and computers to provide unified monitoring and responseto one or more conditions in the regions served by the governmententities in the council.

However, some of the elements may be operated by different entities. Ina building example for diverse building owners, the monitoring servicemay be provided by an entity operating as a service bureau or provider.In this later case, each building owner would own and operate the lightfixtures and LAN in the respective building. The BCS computers and anyterminals in layer L1 may be on the premises or remote, and thatequipment may be owned by the building owner or the service provider.However, such L1 computers will be configured, at least for themonitoring service, by the entity that provides the monitoring service.The computer(s) at the higher levels would likely be owned and operatedby the monitoring service provider, although some may be owned andoperated by other entities with whom the service provider has acooperative agreement, e.g. to a company or government entity that mayagree to respond to conditions sensed on premises monitored by theequipment of the service provider.

The discussion here relates to monitoring of one or more conditionsexternal to the lighting devices over a number of premises and/or over awide geographic area. The intelligence of the devices and the associatedfeedback sensing, however, allows for a wide range of control functionsrelated to the lighting application as well. For example, the samecommunication and computer resources can be used to monitor and controlthe lighting operations of the intelligent lighting devices. Forexample, the fixtures may report conditions of the sources and fixtureelectronics to the control system computers and respond to commands fromthe control system computers to automatically adjust lightingoperations. Condition reports generated by a high level computer can beused to advise appropriate personnel to service particular lightingdevices, e.g. to replace light source elements and/or other devicecomponents when service is appropriate.

The system 10 can utilize lighting devices in a variety ofconfigurations, for various different lighting applications andassociated monitoring functions. Most of the discussion of FIG. 1 aboveassumed that the exemplary devices were configured as fixtures, forexample, as might be mounted in our around the exterior of buildings orfixtures for street or parking lot type outdoor lighting. The system 10may also utilize intelligent light bulbs installed in relativelystandard desk, floor or table lamps or in relatively dumb fixturesconfigured to take light bulbs having standard size and baseconnections. For this later type of lighting device, the power wouldcome from the lamp or fixture, but the source, couplings, sensor andelectronics of the Ctrl./Comm. board forming the intelligent lightingdevice would be contained within the bulb. Communications would use thepower line or wireless transceivers.

To further appreciate the structure and operations of the intelligentlighting devices, it may be helpful to consider some examples. Forpurposes of illustration and discussion, we will consider exemplaryimplementations as light fixtures, although as noted, intelligentlighting devices with sensing and communication capabilities may beimplemented in other forms.

FIG. 2 shows a first example 101 of an intelligent lighting device basedon use of a microcontroller as the device control element, whereas FIG.3 shows a second example 102 of an intelligent lighting device based onuse of a microprocessor (μP) as the device control element. Also, thefirst example utilizes a legacy light source, whereas the second exampleutilizes an incorporated source, e.g. as might be used in a new designor installation. Similar elements in these two examples are identifiedby like reference numerals.

Considering first the example of FIG. 2, the lighting device 101includes a light source 111 implemented as part of a legacy installation112. For example, the legacy installation 112 may be an existing type ofstreet lamp or light fixture utilizing an older more conventional typeof source. In such a case, some or all of the other elements of thelighting device 101 may be configured as a module coupled to the lightsource 111 in the legacy installation 112, e.g. as added to a lightfixture previously configured to support the light source 111. In theexample, the control elements control the light source 111. The lightsource 111 in the legacy installation 112 could be separately controlled(e.g. by a legacy control system or element, such as a switch). In thislater situation, the added elements of the device 101 would mainlyprovide monitoring and communication functions from the location of thelighting device 101.

The exemplary lighting device 101 includes one or more sensor couplingsand one or more sensors as well as communication and controlelectronics. For the legacy installation 112 of the source 111, theother elements of the lighting device 101 are configured as a modulecoupled to the light source 111, e.g. as may be added to a light fixturepreviously configured to support the light source and coupled to thesource 111 via existing control and/or power connections of the source.

In the example of device 102 in FIG. 3, the light source 111 isintegrated into the fixture or the like, in a unified configurationtogether with the one or more sensor couplings, one or more sensors andthe communication and control electronics. Although the source 111 inthe device 102 may be any suitable type of light source, many suchdevices will utilize the most modern and efficient sources available,such as solid state light sources, e.g. LED type light sources.

Each lighting device 101 or 102 is configured to sense at least oneexternal condition not related directly to operations or communicationsof the lighting device. As discussed more later, each device also has aninterface for communications with other system elements. Hence, alighting device 101 or 102 may have as few as one coupling 115 and oneassociated external condition sensor 117. In the examples discussedherein, each lighting device 101 or 102 includes a number of sensorcouplings 115 and associated sensors 117.

The condition or conditions detected by sensors 117 are external in thatthey relate to some aspect observable in the environment around and nearthe lighting device 101 or 102 other than those relating to thefeedback, normal lighting control and/or communications of the device101 or 102. As noted in the discussion of the network example of FIG. 1,some sensed external conditions, like air temp, air quality, andvibration, relate to ambient conditions around or near the fixtureitself; whereas other sensed external conditions, like reflected ordirected light, or like an image or a video of a distant object, relateto external remote conditions that exist at some distance from fixture.Hence, the device examples of FIGS. 2 and 3 include one or more sensorsSa of types for sensing or detecting an ambient external condition andone or more sensors Sr of types for sensing or detecting a remoteexternal condition. Examples of external ambient condition sensors Sainclude a fire detector, a smoke detector, an airborne chemicaldetector, an airborne biological agent detector, a carbon monoxidesensor, an air temperature sensor, an air pressure detector, a humiditysensor, a moisture detector, an air speed detector, and amicro-electro-mechanical system type sensor. By way of another example,a lighting device 11 may include an ambient sensor Sa in the form of aMicro-Electro-Mechanical System (MEMS) for sensing motion, similar togyroscopic devices used in smartphones and the like to senseorientation, movement and direction. Here, MEMS type sensors would sensemagnitude and directions of vibrations of the fixtures 11 due toexternal forces. Collective analysis of vibration measurements, forexample, might indicate an earthquake and the area and magnitude of theimpact. Examples of external remote condition sensors Sr include adirectional light sensor, a video or still image sensor, and a sounddetector. Some of the ambient and remote sensors may be optical devices,each for sensing one or more characteristics of light in theultraviolet, visible or infrared portions of the electromagneticspectrum. Optical remote condition sensor devices may be used, forexample, for sensing direction of light and determining position of anobject. Other examples of remote condition optical sensors includelinear and two-dimensional imaging devices.

In these examples (FIGS. 2 and 3), each external condition sensorcoupling 115 is configured to present a standardized sensor connectioninterface that is compatible with different types of sensors. In thatway, one standardized configuration of the coupling 115 may be used withdifferent types of sensors. Within any one fixture, there may be one,two or more couplings 115 configured to the same standard as well asone, two or more other couplings 115 configured to one or moreadditional standards. Any sensor connection interface supported througha coupling 115 is standardized across at least a number of differentlighting devices 101 or 102 (or 11 in FIG. 1) in that the differentdevices have similar couplings that support the same connection andassociated electrical aspects of the coupling standard. However, thestandardized connection interface in the various lighting devices alsois compatible with a plurality of different types of sensors. Eachsensor 117 connects to the standardized connection interface of one ofthe sensor couplings 115. Each sensor 117 is a device of one of thetypes compatible with the standardized interface provided through astandardized coupling 115.

Although the couplings 115 may support two or more standards for thesensors, as noted, for purposes of further discussion of the examples ofFIGS. 1 and 2, all of the couplings 115 in one device 101 or 102 providethe same standardized interface for various types of sensors 117. Ineither of the multi-sensor examples, Sr sensors may sense the sameremote condition or different remote conditions. Similarly, the Sasensors may sense the same or different ambient conditions. Hence, thereis at least one first type sensor located so as to sense a first one ofa number of conditions external to the lighting device not directlyrelated to operation of the lighting device and at least one secondsensor of a second one of the types different from the first type thatis located so as to sense a second one of the conditions external to thelighting device not directly related to operation of the lightingdevice. Each Sa sensor connects to the standardized interface of one ofthe couplings 115, and each Sr sensor connects to the standardizedinterface of another one of the couplings 115. Each of the sensors Saand Sr is configured to output a signal responsive to the respectivesensed condition via the standardized connection interface of therespective sensor coupling 115.

Intelligent lighting devices of the type discussed herein may have onlythe one or more external condition sensors 117. However, the specificexamples 101 and 102 illustrated in FIGS. 2 and 3 also include one ormore couplings 116 and sensors 118 to detect a condition related tooperation of the lighting device. A device 101 or 102 may include one ormore feedback sensors for sensing operational conditions, such as sourceor circuit temperature, light output intensity, or one or more othercharacteristics of the light produced by the source, which relate tooperation of the lighting device. Such sensors may provide a local orinternal feedback loop at the lighting device 101 or 102 or may enablecommunication regarding the additional condition to another device overa network and associated light source control based on receivingresponsive commands from the other device. Some or all of the lightingdevices may have light activation related sensors, such as ON/OFFswitches, room occupancy sensors, ambient light sensors for controllinglighting in response to ambient light intensity, and light dimmers.Feedback and light activation sensors are referred to collectively asinternal sensors, in that they sense aspects of and/or user inputs tocontrol the internal lighting operations of one or more of the lightingdevices. Examples of sensors 118 to detect a condition related tooperation of the lighting device 101 or 102 include a sensor fordetecting temperature of one or more components of the lighting device,a feedback light sensor for detecting intensity or other characteristicof light produced by the lighting device, an occupancy sensor fordetecting a condition indicative of occupancy of a region to beilluminated by the lighting device and an ambient light sensor fordetecting ambient light near the lighting device. In the examples ofFIGS. 2 and 3, the illustrative devices 101 and 102 each include one ormore couplings 116 and one or more internal condition sensors 118.

The couplings 116 may be standardized in a manner similar to thecouplings 115, or the couplings 116 may be uniquely configured for eachrespective type of sensor 118. In the example, we will assume that thecouplings 116 present a standardized sensor connection interface that iscompatible with different types of internal condition sensors. Thestandard may be the same as or different from the standardizedinterface(s) of couplings 115. Each sensor 118 in turn is configured toconnect to and provide condition responsive signaling via thestandardized interface of the coupling 116. As noted in the discussionof FIG. 1, this third category of sensor provides signal(s) used toenable control of operation of the light source at least in part basedon the condition(s) sensed by the sensor(s) 118.

Each exemplary lighting device 101 or 102 also includes a processorcoupled to the sensor couplings 115 for processing data responsive tothe signals from the sensors 117. However, the two examples utilizedifferent processor implementations.

Consider first the example of FIG. 2. There, the lighting device 101also includes processing and communications elements, in this caseimplemented on a control/communication (Ctrl./Comm.) board 119. Thelighting device 101 includes a Micro-Control Unit (MCU) 121, whichimplements the control logic for the device 101, that is to say,controls operations of the device 101. The MCU 121 may be a microchipdevice that incorporates a processor serving as the programmable centralprocessing unit (CPU) 123 of the MCU and thus of the lighting device 101as well as one or more memories 125 accessible to the CPU 123. Thememory or memories 125 store executable programming for the CPU 123 aswell as data for processing by or resulting from processing of the CPU123. The MCU 121 may be thought of as a small computer or computer likedevice formed on a single chip. Such devices are often used as theconfigurable control elements embedded in special purpose devices ratherthan in a computer or other general purpose device. A variety of PIC16and PIC32 type MCU chips, for example, may be used as the MCU 121 in thelighting device 101.

As noted, the lighting device 101 includes a source 111, which in theexample of FIG. 2 is part of a legacy type installation 112. Power issupplied to the source 111 by an appropriate driver 131. The sourcedriver 131 may be a simple switch controlled by the MCU, for example, ifthe source 111 is an incandescent bulb or the like that can be drivendirectly from the AC current. Although the driver 131 could be anelement on the control/communication (Ctrl./Comm.) board 119, in theexample, the source driver 131 is a part of the legacy installation 112of the source 111, for example, the ballast in an otherwise conventionalfluorescent light fixture. Power for the lighting device 101 is providedby a power supply circuit 133 which supplies appropriatevoltage(s)/current(s) to the control/communication (Ctrl./Comm.) board119 and provides appropriate power to the source driver 131 to power thelight source 111. Although shown separately for convenience, thecomponents of the power supply circuit 133 may be mounted on the sameboard 119 as the control and communication components, depending onconsiderations such as board/housing space, heat generation, etc. In theexample, the power supply circuit 133 receives electricity fromalternating current (AC) mains 135, although the lighting device may bedriven by a battery or other power source for a particular application.Although not shown, the device 101 may have or connect to a back-upbattery or other back-up power source to supply power for some period oftime in the event of an interruption of power from the AC mains 135.

The source driver circuit 131 receives a control signal as an input fromthe MCU 121, to at least turn the source 111 ON/OFF. Depending on theparticular type of source 111 and associated driver 131, the MCU inputmay control other characteristics of the source operation, such asdimming of the light output, pulsing of the light output to/fromdifferent intensity levels, color characteristics of the light output,etc. If the source and/or driver circuit have the capability, the drivercircuit 131 may also provide some information back as to the operationof the light source 111, e.g. to advise the MCU 121 of the actualcurrent operating state of the source 111.

As outlined earlier, the lighting device 101 includes external conditionsensors 117 connected to standardized couplings 115 as wells as sensors118 for sensing conditions related to operations of the source 112 andassociated sensor couplings 116. The couplings 115, 116 provide physicalconnections, electrical signal connections and any power connectionsthat may be necessary to the respective sensors 117, 118. Physical andelectrical connection aspects of each coupling 115, 116 will conform torelevant aspects of the applicable sensor coupling standard. Theelectrical power and electrical signal communication from and/or to thesensors, in accordance with the electrical aspects of the applicablesensor coupling standard, are provided by appropriate input/output (I/O)circuitry connected between the coupling and the MCU 121. On the MCUside, the I/O circuitry provides a signaling link to a port of the MCU121 and conforms to the signaling standard for that port. Depending onthe design implementation for a particular lighting device 101, I/Ocircuitry may include a separate circuit for each coupling, two or moreI/O circuits for groups of two or more couplings or one I/O circuit forall of the included sensor couplings. In the example of FIG. 2, the I/Ocircuitry for the sensor couplings 115 is represented by the externalsensor input/output (I/O) interface 137; and the I/O circuitry for thesensor couplings 116 is represented by the source operations sensorinput/output (I/O) interface 139.

Hence, together, the coupling 115 and the external sensor I/O interfacecircuitry 137 provide physical and electrical connections as well aselectrical power and signal communications for an external conditionsensor 117 that conform to the applicable sensor connection interfacestandard. The signal communications aspects of the standard at leastallow the sensor 117 to provide external condition responsiveinformation to the MCU 121. Although the actual sensing element of asensor may be analog, the information passed to the MCU 121 willtypically be in a standardized digital format. The digital format,however, may vary somewhat as between sensor types, based on associatedapplication programming discussed more, later. Preferably, the MCU portconnection, the I/O interface circuitry 137 and the interface standardthrough the coupling 115 also will allow the MCU to control one or moreaspects of operation of the sensor 117, e.g. to activate a sensor tosense the applicable condition at a time set by the MCU 121, or toselect one of several conditions to be sensed by a mutli-condition typeof sensor 117, or to adjust a sensitivity of the sensor 117, etc.

As noted, in the examples, the couplings 116 also support a standardizedinterface that may be the same as or similar to the interface of thecouplings 115. Hence, together, the coupling 116 and sourceoperation-related sensor I/O interface circuitry 139 provide physicaland electrical connections as well as electrical power and signalcommunications for a source operation-related sensor 118 that conform tothe applicable sensor connection interface standard. The signalcommunications aspects of the standard at least allow the sensor 118 toprovide source operation-related condition responsive information to theMCU 121. Although the actual sensing element of a sensor may be analog,the information passed to the MCU 121 will typically be in astandardized digital format. The digital format, however, may varysomewhat as between sensor types, based on associated programming. TheMCU port connection, the I/O interface circuitry 139 and the interfacestandard through the coupling 116 may allow the MCU to control one ormore aspects of operation of the sensor 118, e.g. to activate a sensorto sense the applicable condition at a time set by the MCU 121, or toselect one of several conditions to be sensed by a multi-condition typeof sensor 118, or to adjust a sensitivity of the sensor 118, etc.

The lighting device 101 also includes a communication interface 141coupled to a communication port of the MCU 121. The interface 141provides a communication link to a telecommunications network thatenables the MCU 121 to send and receive digital data communicationsthrough the particular network. The network may be wired (e.g. metallicor optical fiber), wireless (e.g. radio frequency or free space optical)or a combination of such network technologies; and the interface 141 ina particular installation of the device 101 will correspond to the mostadvantageous network available (based on considerations such as cost andbandwidth) at the location of the installation. In network example ofFIG. 1, the network is a local area network (LAN) 17A or 17B, thereforethe communication interface is of a type for linking to andcommunication through the available LAN. The communication interface 141is therefore accessible by the processor/CPU 123 of the MCU 125, and thecommunication interface 141 is configured to enable the processor tocommunicate information resulting from one or more functions that theprocessor performs in response to the various conditions sensed by thesensors 116 and/or 117 through the LAN or other communications network.

As noted, the MCU 121 includes one or more memories 125. The memories125 store programming for execution by the CPU 123 as well as data to beprocessed or that has been processed by the CPU 123. The programming isshown in block diagram or module form as a program stack at 143.

The programming 143 includes an operating system (OS) 145 and variousapplication programs, which are resident in the memory and execute onthe CPU. The operating system 145 enables execution of the variousapplications, both for local functions and for communications using theinterface 141. Of note for purposes of this discussion, the applicationsoftware includes the software for implementing the control of thelighting device as well as the software for MCU interaction with thevarious connected sensors. For discussion purposes, the example showstwo application programs AP_(s1), AP_(s2), for controlling lightingdevice operations with respect to two different types of sensors. Onetype of sensor may be for one or more of the source operation-relatedcondition sensors 118, but in this example, we will assume that thesensor application program AP_(s1) controls operations in relation to atype of one of the ambient external condition sensors Sa, and the sensorapplication program AP_(s2) controls operations in relation to a type ofone of the remote external condition sensors Sr. Application programs,such as AP_(s1), AP_(s2), are examples of programming for execution bythe processor that corresponds at least in part to the type(s) ofsensors and controls at least one function of the processor responsiveto the condition(s) sensed by the sensor(s). The CPU 123 also will runone or more other application programs 147 from memory 125, to controlvarious other functions of the lighting device 101, such as control ofthe light source 111, interaction with other types of sensors 118 or117, and communications through the interface 141.

The programming 143, either as part of the OS 145 or as a complement tothe OS 145, implements a standard application programming interface(API) 149 for at least the application programs(s) APs relating toexternal condition sensing. Although not separately shown, theprogramming 143 may implement the same or different APIs forapplications related to the source operation-related condition sensors118 and/or other applications to be executed through the OS 145 by theCPU 123. An API, such as 149, provides a standard software interface forexchanges between software components, allowing components tocommunicate and interact. An API standard, for example, can specifycommand formats, response formats, data structures, etc. In this case,the standard sensor API 149 offered or supported by the OS 145 allowsvarious parties, such as different sensor manufactures, to writeapplication programs AP for the MCU 121 to allow the device 101 toutilize different external condition sensors 117.

The application programs AP and the API 145 also enable the MCU 121 tocommunicate information or data generated in response to processing ofsignals or outputs of the sensors 117 so as to implement a standardizedapplication programming interface with respect to the sensor relatedprocessing function(s). The information resulting from processingfunctions of the MCU in turn is communicated through the interface 141and the network in a manner conforming to the standardized applicationprogramming interface. In this way, various devices 101 communicate datarelating to various types of sensors through the network in astandardized format that can be readily processed by other equipmentthat is aware of the format supported by the application programminginterface.

Hence, each application program AP_(s1) or AP_(s2) controls one or morefunctions of the processor (CPU) 123 responsive to the externalcondition or conditions sensed by the respective type of sensors 117.For example, the programming may control how data regarding the sensedconditions is collected, processed and formatted for communication, e.g.so as to conform to relevant aspects of the standard interfacespecification and associated API. The programming 143 may also configurethe processor/CPU 123 to control the light source 111, either based oninternal logic or based on commands received at the device 101 via thenetwork communication. Each application program AP_(s1) or AP_(s2) maycontrol operation in relation to a single one of the sensors 117 or inrelation to some number of two or more of the sensors 117 and/or 118.

The application program corresponding to a particular type of sensorenables the processor 123 to receive data representing the conditionsensed by the sensor 117 and controls at least one function of the CPU123 responsive to the condition sensed by the sensor, such as processingof the data for communication via the interface 141 and the network. Thecontrol function(s) implemented by execution of the application programfor a particular type of sensor may involve other logic in addition orinstead of processing for communications. For example, the applicationprogram may determine timing for detecting a particular condition or foractivating or responding to a particular sensor, e.g. on a periodicbasis so as to reduce processing load and/or communication traffic. Asanother example, the control function relating to a particular conditionmay involve a threshold, either of a value or a change regarding thesensed condition. A program might cause the MCU 121 to react todetection of more than some set amount of a chemical in the atmosphereas an indication of a harmful condition or to update a reportedtemperature when the temperature has changed more than a thresholdamount. The open nature of the lighting devices 101, provided by thesensor interface and associated API supports use of a wide range ofsensor types and an even wider range of program logic for differentnetworked applications of such devices.

Consider next the alternative example of a lighting device 102 shown inFIG. 2. The alternative example of a lighting device 102 includes asomewhat similar source 111. As noted earlier, the source is a newsource integrated in a new installation type implementation of thedevice 102. Although the driver 231 for the source 111 could beseparate, in the example, the source driver circuitry 231 may beimplemented as part of the control and communication board 219 as shown.As discussed earlier, the lighting device 102 also includes the sensors118, 117 and couplings 115, 116 as in the device 101 of FIG. 2. Many ofthe functions/operations of the device 102 are similar to those ofdevice 101, however, the lighting device 102 utilizes a somewhatdifferent control architecture than the MCU based arrangement of thedevice 101 shown in FIG. 2.

Hence, in the lighting device 102 of FIG. 3, the processing andcommunications elements on the control/communication (Ctrl./Comm.) board219 include a microprocessor (μP) 223, which serves as the programmablecentral processing unit (CPU) of the lighting device 102. The μP 223,for example, may be a type of device similar to microprocessors used inservers, in personal computers or in tablet computers or other generalpurpose computerized devices. Such a device typically offers more andfaster processing capabilities than the CPU of a Micro-Control Unit 121like that used in the device 101. Unlike the Micro-Control Unit, programand data storage is external; and instead of specially configured ports,the μP 223 is typically configured to communicate data at relativelyhigh speeds via one or more standardized interface buses, representedgenerally by the bus/arrow 224.

The lighting device includes one or more storage devices, which areaccessible by the μP 223 via the bus 224. Although the lighting device102 could include a hard disk drive or other type of disk drive typestorage device, in the example, the device 102 includes one or morememories 225. Typical examples of memories 225 include read only memory(ROM), random access memory (RAM), flash memory and the like. In thisexample, the memory or memories 225 store executable programming for theμP 223 as well as data for processing by or resulting from processing ofthe μP 223.

As noted, the lighting device 102 includes a source 111, which in theexample of FIG. 3 is an integral part of the device 102. Power issupplied to the source 111 by an appropriate driver 231, in thisexample, included as a component on the control/communication(Ctrl./Comm.) board 219. Although represented as a single element in thedrawing, the driver may comprise a number of elements offering severalcontrol channels for different elements of the light source 111. Forexample, a light emitting diode (LED) implementation of the light source111 may have individually controlled LEDs or strings of LEDs; and forsuch an implementation, the driver 231 would consist of several drivercircuits providing corresponding independent channels of control. Thesource driver 231 provides a source of power and associated control bythe CPU, in this case by the μP 223, similar to the functions providedby the driver 131 in the device 101 of FIG. 2, except that the driver231 includes a bus interface that enables the μP 223 to communicate withthe source driver 231 via the bus 224.

The lighting device 102 includes a power supply circuit 233 coupled tothe AC mains 135, like the supply circuit in the example of FIG. 2,although the circuit 233 and the board 219 will be configured to supplydiver voltage/current to the source driver 231 via the board instead ofthe separate path shown in the example of FIG. 2. As in the earlierexample, the lighting device may be driven by a battery or other powersource for a particular application, or an AC powered device 102 mayhave or connect to a back-up battery or the like to supply power forsome period of time in the event of an interruption of power from the ACmains 135.

The source driver circuit 231 receives control commands from the μP 223via the bus 224, to at least turn the source 111 ON/OFF. Depending onthe particular type of source 111 and the associated driver 231, the μP223 commands may control other characteristics of the source operationsuch as dimming of the light output, pulsing of the light output to/fromdifferent intensity levels, color characteristics of the light output,etc. If the source and/or driver circuit have the capability, the drivercircuit 231 may also provide some information back as to the operationof the light source 111, e.g. to advise the μP 223 of the actual currentoperating state of the source 111.

As noted, the lighting device 102 includes external condition sensors117 connected to standardized couplings 115 as wells as sensors 118 forsensing conditions related to operations of the source 112 andassociated sensor couplings 116. The couplings 115, 116 provide physicalconnections, electrical signal connections and any power connectionsthat may be necessary to the respective sensors 117, 118. Physical andelectrical connection aspects of each coupling 115, 116 will conform torelevant aspects of the applicable sensor coupling standard(s). Theelectrical power and electrical signal communication from and/or to thesensors, in accordance with the electrical aspects of the applicablesensor coupling standard, are provided by appropriate input/output (I/O)circuitry connected between the coupling and the bus 224, much like inthe earlier example of FIG. 2.

Hence, the lighting device 102 includes external sensor I/O circuitry237 and source operation-related sensor I/O circuitry 239. With respectto the respective sensors and couplings, the I/O circuits are similar tothe circuits 137 and 139 in the example of FIG. 2. However, each of thecircuits 237 and 239 includes a bus interface that enables the μP 223 tocommunicate with the respective I/O interface circuit 237 or 239 via thebus 224. Each of the circuits 237 and 239 may be configured to providethe electrical interface for one, two or more of the respective sensorsvia the associated coupling(s).

The lighting device 102 also includes a communication interface 241,which is similar to the communication interface 141 in the earlierexample, in that the communication interface 241 provides two way datacommunication via a network such as a LAN. In the example of FIG. 3, thecommunication interface 241 is of a type having a bus interface toenable the interface 241 to communicate internally with the μP 223 viathe bus 224.

As noted, the lighting device 102 includes one or more memories 225accessible via the bus 224; and those memories 225 store programming 243for execution by the μP 223 as well as data to be processed or that hasbeen processed by the μP 223. The programming 243 includes an operatingsystem (OS) 245, an application programming interface (API) 249, sensortype specific applications such as AP_(s3) and AP_(s4), and otherapplication programming 247, similar to the programming 143 included inthe earlier example. However, here, the programming 243 (particularly OS245 and API 249) is of a type written for the particular type of μP 223.The sensor type specific application programs AP_(s3) and AP_(s4) wouldbe written to conform to the API 249 and to the particular types ofsensors included in the lighting device 102.

Again, application programs, such as AP_(s3), AP_(s4), are examples ofprogramming for execution by the processor that corresponds at least inpart to the type(s) of sensors and controls at least one function of theprocessor responsive to the condition(s) sensed by the sensor(s). The μP223 also will run one or more other application programs 247 from memory225, to control various other functions of the lighting device 102, suchas control of the light source 111, interaction with other types ofsensors 118 or 117, and communications through the interface 241.

At least for the external condition sensors 117 and possibly for thesource operation-related condition sensors 118, the API 249 provides thestandard software interface of the OS to the application programs AP, asin the earlier example. The application programs AP and the API 245 alsoenable the μP 223 to communicate information or data generated inresponse to processing of signals or outputs of the sensors 117 so as toimplement a standardized application programming interface with respectto the sensor related processing function(s). The resulting informationin turn is communicated through the interface 241 and the network in amanner conforming to the standardized application programming interface.In this way, various devices 102 communicate data relating to conditionssensed by various types of sensors 117 and/or 118 through the network ina standardized format that can be readily processed by other equipmentin the higher layers of the system 10 of FIG. 1 that is aware of theformat supported by the application programming interface.

Each application program AP₃ or AP_(s4) corresponding to a particulartype of sensor enables the μP 223 to receive data representing thecondition sensed by the sensor 117 and controls one or more functions ofthe μP 223 responsive to the external condition or conditions sensed bythe respective type of sensors, in a manner similar to the applicationprograms AP in the earlier example.

The examples of FIGS. 1-3 utilized monitoring, control andcommunications elements that were substantially integrated with thefixture and fairly closely coupled to the light source of the fixture.In those examples, elements were provided that sensed conditions relatedto light source operation and could respond based on internal logicand/or commands from higher level control computers (e.g. to control thelight source). However, other configurations are contemplated, forexample, that may not utilize the elements on the board to control thelight source, may provide additional output or control capability basedon internal logic and/or commands from higher level control computersand/or to provide communication connectivity to other devices in thevicinity (e.g. for communication of other devices through the network(s)of FIG. 1). In many cases where there is an installed base of lightfixtures, it may be practical to add a module providing monitoring andcommunication capabilities to each existing fixture to add the desiredintelligence, etc.

FIGS. 4 and 5 relate to such an example of a lighting device 311 inwhich the monitoring and communication elements are implemented in amodule 312 separate, which is attached to or mounted in the vicinity ofa light fixture 313. However, the light fixture 313 in this example is alegacy fixture, and the elements within the module 312 do not controlthe light source 314 included with the associated fixture 313. The lightfixture 313 and the module 312 together, in this example, form thelighting device 311. FIG. 4 shows the elements of the lighting device311, whereas FIG. 5 is a block diagram illustration of the electronicelements of the monitoring and communication module 312.

The example of FIG. 4 utilizes a cobra-head type device as the lightfixture 313. The cobra-head fixture is attached to a beam or arm 315supported by a lamp post or light pole 316, although other mountingstructures may be used. Light fixture implementations and mountingarrangements like those shown in FIG. 4 are common in street and parkinglot applications. Of course, the monitoring and communication module 312of FIG. 4 and FIG. 5 may be used with other types of legacy lightfixtures and/or in other types of applications.

The light fixture 313 may include any light source 317 that isappropriate for the intended lighting application. The fixture includesa housing 318 that encloses the light source and other elements andprovides the mechanical attachment to the supporting beam 315. Thehousing 318 also supports a transparent or diffusely transmissive cover319 through which the source 317 emits light.

As in earlier examples, electrical power is obtained from alternatingcurrent (AC) mains 135, although the light source 317 may be driven by abattery or other power source for a particular application. AC powerlines typically extend up through the pole 316 and the beam 315 andconnect to the fixture 313, although such lines are omitted for ease ofillustration.

The lighting device 311 also includes a controller 321 for controllingoperation of the light source 317. The controller 321 could be external,but in the example, the housing 318 also encloses the controller 321.

Although other more sophisticated control functions may be provided byan appropriate implementation of the controller 321, for discussionpurposes, we will assume that the controller simply switches power tothe source 317 ON and OFF. Depending on the type of light source 317,the controller 321 may include power conversion circuitry such as aballast or the like to convert the power obtained from the AC mains 135to an appropriate voltage/current power for the particular light source317.

The ON/OFF switching by the controller 321 may be based on a simpleinput switch, commands received from an external device via the powerlines or another device, etc. In the example, the light fixture 313includes a light sensing transducer 323, such as a photocell. Thetransducer 323 provides a signal that is related to the intensity ofdaylight reaching the transducer on the exterior of the fixture 313. Thecontroller 321 in the example turns power to the light source 317 ONwhen the intensity of light detected by the transducer 323 falls to orbelow a threshold, e.g. to turn ON the source 317 as night is falling.Conversely, the controller 321 turns power to the light source 317 OFFwhen the intensity of light detected by the transducer 323 reaches athreshold, e.g. to turn OFF the source 317 as the sun rises in themorning. The source is kept ON in the dark of night, and the source iskept off during the daytime when sunlight is fairly plentiful.

In this example, the cobra head light fixture 313 is configured anoperates in a conventional manner. The fixture may be an existing devicethat need not be modified, with respect to power and operationalcontrol.

In an implementation where the fixture 313 is a legacy device, thefixture is enhanced or upgraded by the addition of the monitoring andcommunication module 312. In the example, the module 312 is mounted byattachment to an underside surface of the housing 318 of the cobra headfixture 313. However, the module 312 may be added and mounted inassociation with the fixture 313 at any location and/or in any mannerthat is suitable for a particular installation and/or a particularapplication.

Existing light fixtures such as the fixture 313 have connection topower, represented by the AC mains 135 in the drawing. The module 312could be supplied power in other ways from other sources, but typically,the module 312 will utilize the existing source of power available atthe light fixture, eliminating the need for separate power and/orwiring. Hence, in the example, the module 312 connects to and obtainspower from the AC mains already present in the lighting device forpowering the light source 317. Although other connections may be used,e.g. depending on the location and/or mounting of the module 312, in theexample, the module 312 has a connection to the AC main lines power 135at a point in the housing of the cobra head light fixture 313.

The monitoring and communication module 312 is a layer L1 lightingdevice and communicates through a network with L1 layer computers, anddata is processed and communicated with the higher layernetworks/computers, in the hierarchical system of FIG. 1. Since thenetworks and control computers of the hierarchy are the same as orsimilar to those in the earlier example, those system elements areomitted from the illustration and further discussion with respect to theexample of FIGS. 4 and 5. With respect to FIG. 4, the simplifiedillustration shows a network link to/from the monitoring andcommunication module 312. This link may be wireless, although in theexample it is a hard link such as a wire or optical network cable. Anysuitable link may be used.

The monitoring and communication module 312 may perform sensorresponsive monitoring and related communications only. However, for atleast some system installations, it may be desirable to add furtherfunctional elements on or near the fixture that operate in some mannervia the monitoring and communication module 312. In the example of FIGS.4 and 5, the additional elements include a local wireless transceiver325, such as a WiFi access point. The module 312 provides connectivityfor the WiFi local wireless data transceiver 325 to the data networkused by the module 312. In this way, the lighting device may provide ahotspot for Internet access or the like in the vicinity of the lightingdevice 311. By providing modules 312 and WiFi access points 325 onvarious street lamps around a city or enterprise campus, the city orcampus can offer outdoor wireless Internet service, e.g. as a publicservice and/or for use by city or enterprise personnel.

The additional or ancillary devices provided in the vicinity of thelight fixture may also include any of a wide range of devices that maybe controlled via communications through the network and the monitoringand communication module 312 of the lighting device 311. Just by way ofone example, such added equipment on one or more lighting devices 311may be used to provide information to people in the vicinity of thefixture 313. Messages could be provided via the WiFi access point 325 touser data devices, or by a Bluetooth transceiver (not shown) for exampleto equipment in passing vehicles.

In the illustrated example, the additionally controlled equipmentincludes a visible message output device, such as a video monitor ordigital sign board, represented generally by the video screen 327. Thedata network enables communications of commands and/or data to themodule 312 to control information output via the video screen 327. Thevideo screen 327, for example, may provide advertising or otherinformation of general interest; or as shown by way of example, thescreen may be used to provide a warning of danger or an announcement ofinstructions to the public in the vicinity of the lighting device 311.

The device 311 may also offer audible information output, and for thatpurpose, the exemplary device 311 also includes one or more loudspeakers329. Much like for operation of the video screen 327, the data networkenables communications of commands and/or data to the module 312 tocontrol information output via the one or more loudspeakers 329, for anyparticular purpose deemed suitable by the service provider/operator ofthe system of FIG. 1.

Turing now to FIG. 5, we next consider an example of an implementationof the monitoring and communication module 312. The module 312 could beimplemented using an MCU based architecture similar to that used in theexample of FIG. 2. For purposes of an illustrative example fordiscussion here, however, FIG. 5 shows an architecture for the module312 that is based on a microprocessor (μP) and bus architecture similarto that of the example of FIG. 3. Hence, elements shown in FIG. 5 thatare the same as elements shown in the example of FIG. 3 use the samereference numerals and are discussed again here more briefly, since thereader should be familiar with or able to refer back to the earlierdiscussion of such elements for additional information regarding suchsimilar elements.

The monitoring and communication module 312 includes a power supplycircuit 233 coupled to the AC mains 135, like the supply circuit in theexample of FIG. 3. As in the earlier examples, the module 312 may bedriven by a battery or other power source for a particular application,or an AC powered device 312 may have or connect to a back-up battery orthe like to supply power for some period of time in the event of aninterruption of power from the AC mains 135.

The power supply circuit 233 provides appropriate power to drive thevarious elements on the control and communication board 331. The powersupply circuit 233 may be mounted on the board 331 or a separate unit asshown.

The processing and communications elements on the control/communication(Ctrl./Comm.) board 331 include a microprocessor (μP) 223, which servesas the programmable central processing unit (CPU) of the module 312. TheμP 223 is configured to communicate data via one or more standardizedinterface buses, represented generally by the bus/arrow 224. Themonitoring and communication module 312 also includes one or morestorage devices, which are accessible by the μP 223 via the bus 224.Although the module 312 could include a hard disk drive or other type ofdisk drive type storage device, in the example, the device 102 includesone or more memories 225, such as ROM, RAM, flash memory or the like. Inthis example, the memory or memories 225 store executable programmingfor the μP 223 as well as data for processing by or resulting fromprocessing of the μP 223. Although not shown in this latest drawing forconvenience, the programming stored in the memory or memories 225include the operation system as well as the application programs (AP)for use with specific sensors.

The monitoring and communication module 312 also includes acommunication interface 241, which is similar to the communicationinterfaces in the earlier examples, in that the communication interface241 provides two way data communication via an external network such asa LAN. In the example of FIG. 5, like that of FIG. 3, the communicationinterface 241 is of a type having a bus interface to enable theinterface 241 to communicate internally with the μP 223 via the bus 224.

In this example (FIGS. 4 and 5), the monitoring and communication module312 also supports local wireless communication. As noted in thediscussion of FIG. 4, the specific example uses a WiFi type wirelessaccess point transceiver 325 for local wireless data communication withdata devices in the vicinity of the intelligent lighting device 311.Hence, the monitoring and communication module 312 includes a secondcommunication interface 333. The interface 333 would be of a standardtype configured for local communications with the particular type ofdevice 325. In the example WiFi type example of these drawings, thesecond communication interface 333 would typically be an Ethernet typeLAN interface. An Ethernet cable would provide a connection from theinterface 333 in the module 312 to the WiFi type wireless access point325. Like the interface 241, the second communication interface 333 isof a type having a bus interface to enable the interface 333 tocommunicate internally with the μP 223 and/or the interface or otherelements of the board 331 via the bus 224. For example, under control ofthe μP 223 when executing programming from the memory or memories 225,the interfaces 333 and 241 may provide two-way data communications fordevices utilizing the WiFi type wireless access point 325 to access theInternet. The WiFi type wireless access point 325 and the secondcommunication interface 333 may also enable data devices in the vicinity(with appropriate access privileges) to access the μP 223, e.g. toobtain monitoring data, module operational information or the likeand/or to provide control commands and/or new programming to the module312.

As in the lighting devices in the earlier examples, the lighting device311 includes external condition sensors 117 connected to standardizedcouplings 115. In this case the couplings 115 are part of the module312; and the sensors 117 are attached to and supported together with themodule 312. The couplings/sensors could be mounted separately andconnected to the module 312. The couplings 115 provide physicalconnections, electrical signal connections and any power connectionsthat may be necessary to the external condition sensors 117. Physicaland electrical connection aspects of each coupling 115 will conform torelevant aspects of the applicable sensor coupling standard(s). Theelectrical power and electrical signal communication from and/or to thesensors 117, in accordance with the electrical aspects of the applicablesensor coupling standard, are provided by appropriate input/output (I/O)circuitry 237 connected between the coupling and the bus 224, as in theearlier example of FIG. 3. The external sensor I/O circuitry 237includes a bus interface that enables the μP 223 to communicate with therespective I/O interface circuit 237 via the bus 224. The externalsensor I/O circuitry 237 may be configured to provide the electricalinterface for one, two or more of the sensors 117 via the associatedcoupling(s).

Although not shown in this example, the monitoring and communicationmodule 312 may include one or more sensors and associated couplings thesame as or similar to the sensors 118 and couplings 116 for sensing oneor more conditions that relate to operation of the light source. In sucha case, the communication module 312 would also include sourceoperation-related sensor I/O circuitry similar to circuitry 239 in theexample of FIG. 3. Although the module 312 does not control the sourceoperation of the fixture 313, the information obtained by suchadditional sensing may be reported to the higher layer control computersas it may be useful in some system applications, e.g. to report on howwell or poorly particular light fixtures are operating.

As noted in the discussion of FIG. 4, the intelligent lighting device311 may support communication with and/or control of additional orancillary devices provided in the vicinity of the light fixture 313.Although a wide range of such additional or ancillary devices may beprovided for various applications of the device 311 in the context of aparticular service provided by the system of FIG. 1, the specificexample provided a video screen 327 and loudspeakers 329 for localinformation output. The monitoring and communication module 312 of thedevice 311 will include one or more drivers for communication withand/or control of any additional devices included in or associated withdevice 311. Hence, in this example, monitoring and communication module312 includes one or more bus connected audio and/or video (A/V) drivers335. Depending on the form/standard of the link to the video screen 327and loudspeakers 329, the module may use a single combined driver or twoseparate drivers. The A/V driver(s) may be similar to drivers used inpersonal computers to drive an external monitor and speakers. Eachdriver 335 is of a type having a bus interface to enable the interface335 to communicate internally with the μP 223 and/or other elements ofthe board 331 via the bus 224. For example, the module 312 may receivecommands to provide audio and/or video output as well as the desiredinformation content in packetized form via the network. The μP 223controls the driver(s) 335 to cause the video screen 327 andloudspeakers 329 to provide outputs, and the driver(s) convert thereceived content to appropriate format signals so that the content isoutput in a presentable form as audio and video via the video screen 327and loudspeakers 329.

The program memory for storing executable programming often is thememory on the control and communication board (either within the MCU orcoupled to the μP via the bus in our three examples, FIGS. 2, 3 and 5).As outlined earlier, the exemplary sensors 118, 117 include at leastsome circuitry for processing the output of the transducers included aspart of the sensors. In such a sensor, the circuitry receives the signalfrom the transducer(s) in the sensor and produces an output via thecoupling that conforms to the signaling aspects of the sensor couplingstandard, e.g. as a standard analog level signal on one or more pinsdesignated for an analog connection and/or as appropriately formatteddata on the pins designated for data outputs. The sensor circuitry mayalso receive standard control signals, e.g. digital command signals,over designated for data inputs to the sensor. Many implementations ofsuch sensors will include a programmable processor, and some sensorconfigurations may include memory. If included as part of the sensor,the memory may contain the applications program (AP) for the relevanttype of sensor. In such a case, the CPU may directly access the programin the sensor memory, or the application program AP may be uploaded fromthe sensor memory to the appropriate memory on the control andcommunication board.

The structure and operation of the intelligent lighting devices 101, 102and 311, as outlined above, were described by way of example, only.

As shown by the above discussion, the higher layer functions relating tomonitoring of one or more conditions external to the lighting devicesnot directly related to operational performance of the respectivelighting devices, communications and related data processing andcondition responsive functions may be implemented on various computers(at layers L2 to L4) connected for data communication via the componentsof a local or wide area network as shown in FIG. 1. Although specialpurpose devices may be used, such devices also may be implemented usingone or more hardware platforms intended to represent any of the variousavailable types of general purposes programmable devices, albeit with anappropriate network connection for data communication and appropriateprogramming to implement the functions discussed herein.

FIGS. 6, 7 and 8 provide functional block diagram illustrations ofgeneral purpose computer hardware platforms. FIG. 6 illustrates anetwork or host computer platform, as may typically be used to implementa host or server, such as one of the computer 13A, 13B, 23A, 23B or 27.FIG. 7 depicts a computer with user interface elements, as may be usedto implement a personal computer or other type of work station orterminal device, such as one of the computers 15A or 29 in FIG. 1,although the computer of FIG. 7 may also act as a server ifappropriately programmed. The computer of FIG. 8 represents an exampleof a mobile device, such as a tablet computer, smartphone or the likewith a network interface to a wireless link. It is believed that thoseskilled in the art are familiar with the structure, programming andgeneral operation of such computer equipment and as a result thedrawings should be self-explanatory.

A server (see e.g. FIG. 6), for example, includes a data communicationinterface for packet data communication via the particular type ofavailable network. The server also includes a central processing unit(CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. Of course, theserver functions may be implemented in a distributed fashion on a numberof similar platforms, to distribute the processing load.

Also, a computer configured as a server with respect to one layer orfunction may be configured as a client of a server in a different layerand/or for a different function. For example, the intelligent lightingdevices 11 may operate as client devices of server functions implementedby L2 computers such as 13A and 13B, whereas the same L2 computers 13Aand 13B may function as clients with respect to at least some of thehigher layer computers such as a computer 23A or 23B. Similarly,computers such as 23A, 23B that function as servers with respect tocomputers in the lower layer may be configured as client devices withrespect to higher layer computer(s) such 27 configured as servers. Ifmore effective for a particular system application, client-serverarrangement outlined above could be inverted, so that the higher layercomputers would be configured as clients with respect toserver-configured computers in the next lower layer. Also, terminaldevices often are configured as client devices.

A computer type user terminal device, such as a desktop or laptop typepersonal computer (PC), similarly includes a data communicationinterface CPU, main memory (such as a random access memory (RAM)) andone or more disc drives or other mass storage devices for storing userdata and the various executable programs (see FIG. 7). A mobile device(see FIG. 8) type user terminal may include similar elements, but willtypically use smaller components that also require less power, tofacilitate implementation in a portable form factor. The example of FIG.8 includes a wireless wide area network (WWAN) transceiver (XCVR) suchas a 3G or 4G cellular network transceiver as well as a short rangewireless transceiver such as a Bluetooth and/or WiFi transceiver forwireless local area network (WLAN) communication. The computer of FIG. 7is shown by way of example as using a RAM type main memory and a harddisk drive for mass storage of data and programming, whereas the mobiledevice of FIG. 8 includes a flash memory and may include other miniaturememory devices.

The various types of user terminal devices will also include varioususer input and output elements. A computer, for example, may include akeyboard and a cursor control/selection device such as a mouse,trackball, joystick or touchpad; and a display for visual outputs (seeFIG. 7). The mobile device example in FIG. 8 touchscreen type display,where the display is controlled by a display driver, and user touchingof the screen is detected by a touch sense controller (Ctrlr).

The hardware elements, operating systems and programming languages ofsuch user terminal devices also are conventional in nature, and it ispresumed that those skilled in the art are adequately familiartherewith. Of note for purposes of this discussion, each type ofcomputerized device will store and execute programming, including anoperating system (OS) appropriate to the particular device and one ormore application programs (APs). The programming will also implement anapplication programming interface (API) that allows the applicationprograms to execute through OS on the processor(s) that function as thedevice CPU. At least some of the application programs (APs) arespecifically written to configure the respective computerized devices toimplement the functions of the L2 to L4 layer computers of the system10, as described herein.

In several examples, the intelligence and sensors are integrated with orattached to the fixture or other element that incorporates the lightsource. However, for some installations, there may be some separationbetween the fixture or other element that incorporates the light sourceand the electronic components that provide the intelligence andcommunication capabilities. Also, in the examples, the sensors areincorporated in the fixture or module that houses the electroniccomponents that provide the intelligence and communication capabilities.However, depending on the condition(s) to be sensed and/or theparticular installation, the sensors and standardized couplings may bemounted somewhat separately and connected or otherwise coupled to theelectronic components that provide the intelligence and communicationcapabilities.

The monitoring and communications elements may be applied to or combinedwith any type of light source. Hence, the intelligent lighting devicesmay be any desirable type of indoor or outdoor lighting device, signallighting devices such as traffic lights, lighted signage, etc. A systemlike that of FIG. 1 may include within the one system any number ofthese different types lighting devices. A system operated by a city ormunicipality, for example, might add intelligence to street lights ofvarious types, traffic lights and various types of indoor buildinglights in buildings used by the government. A system operated by a stateor country might add intelligence to lights of the types mentioned withregard to the city, in each city or town of the state or country as wellas to highway lights and sign lighting along roads, streets and highwaysbetween cities and towns in the jurisdiction. The broader the coverage,the more varied the types of lighting devices that are likely to beincluded in the system.

A system run by a private enterprise, either to monitor its own premisesor to provide monitoring and the like as services to its customers mightinstall intelligent lighting devices or add intelligent modules likethat of FIG. 5, for indoor and outdoor lighting applications as varioustypes of lighting devices on private property. If such an enterprisesells the services to a government, then the enterprise would installand operate a system like that described earlier for a city, state orcountry. One service provider enterprise might also sell the servicesboth to government and to private parties, essentially resulting in anoverall system that includes both government and private installationsof the intelligent lighting devices and could combine data from all ofthe intelligent lighting devices.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”“includes,” “including,” or any other variation thereof, are intended tocover a non-exclusive inclusion, such that a process, method, article,or apparatus that comprises a list of elements does not include onlythose elements but may include other elements not expressly listed orinherent to such process, method, article, or apparatus. An elementproceeded by “a” or “an” does not, without further constraints, precludethe existence of additional identical elements in the process, method,article, or apparatus that comprises the element.

Unless otherwise stated, any and all measurements, values, ratings,positions, magnitudes, sizes, and other specifications that are setforth in this specification, including in the claims that follow, areapproximate, not exact. They are intended to have a reasonable rangethat is consistent with the functions to which they relate and with whatis customary in the art to which they pertain.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

What is claimed is:
 1. An apparatus for use with a light source, theapparatus comprising: a first sensor coupling configured to present: afirst standardized sensor connection interlace, the first standardizedsensor connection interface being compatible with a first sensor; secondsensor coupling configured to present a second standardized sensorconnection interface, the second standardized sensor interface beingcompatible with a second sensor; wherein the first sensor is configuredto sense a first external condition among a plurality of externalconditions in a first location around a fixture containing the lightsource, wherein first external condition is not directly related tooperation or control of the light source, the first sensor beingconfigured to output a first signal responsive to the first sensedexternal condition via the first standardized sensor connectioninterface of the first sensor coupling; wherein the second sensor isconfigured to sense a second external condition among the plurality ofexternal conditions in a second location around the fixture containingthe light source, wherein the second location is different from thefirst location, wherein the second external condition is not directlyrelated to operation or control of the light source, the second sensorbeing configured to output a second signal responsive to the secondsensed external condition via the second standardized sensor connectioninterface of the second sensor coupling; a processor coupled to thefirst sensor coupling and the second sensor coupling; a communicationinterface accessible by the processor; a memory accessible to theprocessor; and programming stored in the memory, wherein execution ofthe programming by the processor configures the processor to implementfunctions, including functions to: receive, in a standardized signalformat, the first signal from the first sensor and the second signalfrom the second sensor; deliver, in a standardized data format and basedat least in part on the first signal and in part on the second signal,first data, representing the first external condition sensed by thefirst sensor and the second external condition sensed by the secondsensor to a First application program; deliver, in the standardized dataformat and based at least in part on the first signal and in part on thesecond signal, second data representing the first external conditionsensed by the first sensor and the second external condition sensed bythe second sensor to a second application program; enable processing ofthe first data representing the first sensed external condition and thesecond sensed external condition by the processor on behalf of the firstapplication program; enable processing of the second data representingthe first sensed external condition and the second sensed externalcondition by the processor on behalf of the second application program;communicate, in a standardized communications format enabled by theprogramming and to a first destination, first information resulting fromprocessing of the first data representing the first sensed externalcondition and die second sensed external condition; and communicate, inthe standardized communications format enabled by the programming and toa second destination, second information resulting from processing ofdie second data representing the first sensed external condition and thesecond sensed external condition.
 2. The apparatus of claim 1, whereinthe first external condition is same as the second external condition.3. The apparatus of claim 1, wherein the first external condition isdifferent than the second external condition.
 4. The apparatus of claim1, wherein the function to communicate the first information and thefunction to communicate the second information both utilize thecommunication interface.
 5. The apparatus of claim 1, further comprisinga second communication interface, wherein: the function to communicatethe first information utilizes the communication interface; and thefunction to communicate the second information utilizes the secondcommunication interface.
 6. The apparatus of claim 5, further comprisinga local wireless transceiver coupled to the second communicationinterface.
 7. The apparatus of claim 1, further comprising: a modulehousing containing at least the processor, memory and communicationinterface, wherein the housing is configured for mounting together witha fixture containing the light source.
 8. The apparatus of 1, whereinthe processor also is coupled to control the light source.
 9. Theapparatus of claim 1, further comprising: an output driver, coupled forcontrol by the processor, configured to drive an information outputdevice coupled to the apparatus, wherein fort her execution of theprogramming by the processor further configures the processor toimplement functions, including functions to: receive, from a network viathe communication interface and in the standardized communication formatenabled by the programming, information for local output; and operatethe at least one output driver to cause the information output device toreproduce the received information.
 10. The apparatus of claim 1,wherein the sensor coupling is compatible with analog and digitalsignals.